|
|
![]() |
Week of August 20th, 2001
Last Updated: August 27, 2001 00:37
Monday
Tuesday
Wednesday
Thursday
Friday
Saturday
Sunday
Most Recent
Last Week
Next Week
Insights Index
Daynotes.com
Email: tom@syroidmanor.com
See Tuesday.
YES... YES... YES... [Meg Ryan's faked orgasm scene fades from view...]
[strut, strut, strut] He's da' Man. [turn, reverse direction] [strut, strut, strut] He's da' Man... [as he sheaths his bloody sword].
I would have posted this last night, but I was too busy sitting on the porch, notebook in my lap, basking in my accomplishments, and telling everyone who would listen what an incredibly bright guy I am [heh-heh].
-oOo-
Needless to say, I have triumphed over both evil and the "dark forces" yet again.
Phaedrus dual boots Windows 2000 and SuSE 7.2 (using LILO), partitioned as follows:
/hda1 (NTFS) 10G Windows 2000
/hda2 (swap) 512M
/hda3 (ReiserFS) 3G /
/hda4 (extended)
/hda5 (ReiserFS) 2G /var
/hda6 (ReiserFS) 2G /usr/local
/hda7 (ReiserFS) 2.5G /home
Everything has always worked under Win2K. Everything now also works under SuSE. I have sound, USB, PCMCIA card management, all filesystems are ReiserFS (and MAN am I glad I went with that decision given the number of hard resets I've had to do over the past few days!), the kernel is at 2.4.4 (with plans to move to 2.4.9 when time permits), all packages are current, networking works, KDE is at 2.2.0, XFree86 is at 4.1.0, all 3 pointing devices work as advertised, and best of all, my KDE desktop starts at 1600x1200 in glorious 32bit color with anti-aliasing. KDE is stunningly beautiful on my 15" LCD. For the first time I am running a Linux desktop that equals (and in some ways surpasses) the clarity and richness of my Windows desktop.
And that, folks, is something that continues to thrill me each and every time I type startx.
Here is a preliminary step-by-step (I intend to produce a fully detailed HOWTO sometime over the course of the next two weeks -- again, as time permits):
* Sunday night I did YALI -- a clean install of SuSE 72. Default package selection (No StarOffice 5.2); all filesystems ReiserFS.
* Before I quit for the night I used SuSE's YAST tool to update the system -- told it to go forth and update "all" packages (330 files), then hit the pillow.
* I awoke Monday AM to a fully updated system; time to start some basic tweaking...
* First I copied over my custom lilo.conf file from Hydras (via SCP) and rebooted to ensure I could (a) boot into Windows, (b) boot back into Linux, and (c) my console font and configuration was the way I wanted it.
* Next I edited /etc/rc.config and enabled DMA, APM, IRDA, and several other minor twiddles of the dial (Mmm. Note to Self: Save your rc.config file somewhere safe...).
* Next I downloaded and installed all necessary files to bring KDE up to version 2.2.0.
* Then I downloaded and updated XFree86 to 4.1.0.
* Time to generate a base XF86Config file to get me going -- I used SAX2 and plugged in some default values.
* For the first time, I tried to run X. It failed to initialize as I knew it would.
* Next up: Download and install the latest NVidia drivers (http://www.nvidia.com). I followed the instructions for installation under SuSE to the letter.
* I then added the following line to /etc/modules.conf: options NVdriver NVreg_Mobile=1 (this one wasn't documented anywhere; I discovered it in a README for installing NVidia drivers under RH 7.1).
* Reboot.
* At this point in time, I could start KDE, although only as root (Hint: chmod 755 /etc/X11/XF86Config) and only at 1024x768/16bit color depth. Oh yeah, and no mouse cursor.
* One, add option "HWcursor" to the device section of XF86Config; two, tweak the drivers and options (under InputDevice) one at a time until all pointing devices worked (as a nice added bonus, I also managed (without consciously trying) to configure things so my MS scroll wheel works in all KDE apps.
* Finally, it was time to roll up my sleeves and tweak the "Screens" section until I could get 1600x1200 resolution and 32 bit color. I won't provide all the gorey details; suffice to say it took three hours, many system lockups (who said you can't lockup a Linux box?), several outbreaks of bad language, and the correct polar orientation. My final XF86Config file for all the world to see. It's not perfect yet, but it works. For example, I can dump most of the font references in the "Files" section. And while I get 1600x1200 32bit color when I log in as 'tom', I get an oversized "virtual" screen at 16bit color when I log in as 'root'. Dunno.
I've been pounding on the system for 24 hours now. It's stable and very useable. As always, I have a few minor annoyances I've yet to resolve.
Sound works under KDE when logged in a 'root'; the speakers click, but I get nothing when logged in as 'tom'. I think when I resolve the above "virtual desktop" issue (when root), I'll also fix the sound problem. I've come to find that an incorrectly configured device or section in XF86Config can -- at times -- disable sound. And the device that's not correctly configured will have no relationship (or hardware linkages) to sound whatsoever. Cosmic.
I have to figure out where I go to assign a "Meta" key; several programs use it (eg, Mulberry).
I have no up and down keyboard arrows under SSH. Need them to run SMIT on Hydras.
The file (or daemon?) /opt/kde2//bin/artsd (yes, a ps -ef output shows two backslashes in the pathname) now and then freezes KDE when I try to exit. I need to find out what artsd does, whether I need it, how to disable it if I don't, or how to fix the problem if I can't.
I've also come to find out the latest NVidia drivers (1.0-1251) are buggy in one crucial regard. If I lock up KDE for any reason (such as the above exit problem), the next time I try to run it the system locks to a hard reset. Apparently NVidia is aware of the problem and they're working on it.
Time to get some work done. It's going to be a very busy week for me -- I'll do my best to post every day, but no promises.
This morning I experienced the cutting edge of technology, and I like it a lot. I sat on the back deck, Phaedrus in my lap (the proper place for a laptop, of course), coffee within reach, and checked my email. No wires. Very cool.
-oOo-
FedEx showed up yesterday with a goody box from Linksys. The contents included:
a Wireless Network PCMCIA Card (WPC11)
a Wireless USB Network Adapter (WUSB11)
and an EtherFast Wireless Access Point + Cable (4 port) Cable/DSL Router (BEFW11S4)
Talk about a kid in a candy store. Heh-heh-heh. I quickly rifled through each box in turn, then gathered them all up in my arms and disappeared downstairs "to my lab".
Twenty-five minutes later, I emerged, laptop under my arm. I sat down at the kitchen table, opened IE, and proceeded to surf. Everything was installed, connected, configured, and working as advertised. In twenty-five minutes I had added a complete wireless segment to my LAN. And not once did I have to crack a manual or puzzle my puzzler over something. Good grief... TWO pleasant Out-of-Box experiences in six weeks. What in the world is computing coming to?
The Wireless PCMCIA card went in my laptop, of course. I plugged it in, Win2K popped up a "Hardware Found" dialog, I inserted the CD provided, and pointed the Wizard to the WIN2000 directory. First piece installed and configured.
Next, I unpacked the BEFW11S4 hub/router/base station. It stacked nicely on top of my existing Linksys pile: an 8-port Router (BEFSR81) and 5-port switch (EZXS55W). I flipped up the little "rabbit ears", plugged my network cable into a port, opened IE, and typed: http://192.168.1.1. Up popped the familiar Linksys administrative page. Everything identical to my 8-port plus the requisite wireless configurations. I changed the password, entered my second static IP, and changed the device IP to 192.168.1.2 (my other router already uses the 1.1 IP). I then added a cable to uplink my 8-port router to the wireless router so I could access the servers on the other LAN segment (Hydras, Raidserver, etc.).
Presto. I could surf the net from Phaedrus using the wireless PCMCIA card.
Next I unpacked the USB Network Adapter, unplugged the network cable that runs from the 8-port router, down the hall, into the bedroom, and into Leah's system. I plugged the USB device into an open port, and again, up popped the Win2K "Found New Hardware" Wizard. Insert supplied CD, point to the WIN2000 directory, install drivers. I disabled the existing 10/100 network card icon, and the lights on the USB adapter immediately started to blink. Ta and Da. Leah now had wireless network access.
Needless to say, thinking about the steps I took and typing this entry took longer than setting everything up.
I really like products that ship with the above "no-brainer" installation routines. Congratulations Linksys, you've done it again -- I'm impressed.
I certainly don't expect the configuration process to be as seamless under Linux (if I can get the PCMCIA card configured at all -- haven't even tried yet), but Linksys do not market their products to the Linux community. Yet. Which is OK. They strive to target a specific market with quality products and good installation/configuration routines. And they succeed, IMHO. Recommended.
Two minor issues to note: One, the cable required to uplink between my existing LAN/router and the new wireless AP has to be a cross-over cable. If I didn't happen to have such an animal in my cable box, I would have been sunk. Linksys: Suggest you throw a short 6-8" cross-over cable in the box as you did with my 8-port. It would only cost you pennies, and it's a nice touch to have everything in the box you need to make things work. For example, the USB network adapter comes with a USB cable. Two, enabling power management on the PCMCIA card causes the device to stop working. No, I haven't checked for new and/or updated drivers. I will this afternoon, though. Plus any new firmware updates for the AP.
-oOo-
Ken Scott wrote last time to inform me the artsd daemon is used by KDE to produce desktops sounds, etc. Which makes sense. That explains why I have sound as 'root' (no artsd daemon errors) and no sound as 'tom' (consistent artsd errors and occasional "full stop" lockups). Now to finger out why the daemon is exhibiting the behavior it is, and how to fix it. Might just be something that will have to be resolved with the next incarnation of KDE. Thanks Ken. More as I know more.
If my world got any busier, I wouldn't even have time to put my feet in the stirrups... Good grief. When will I learn...
I've been editing a document since mid-morning when I finally rec'd it -- only 12 hours late (#$#!*& authors... mumble, mumble). I'm not even close to being satisfied, but it will have to do because it's due today [translation: before midnight whatever local time is convenient]. Now all I have to do is translate it to XML and compile it, which is going to take about six hours. So Yep, it's going to be tight.
I tried to compile the Linux driver for my wireless LAN this morning (while waiting for said document to arrive... ). No Joy. Rats and Bother too. My 'script' file is here. If anyone can help, I'd appreciate it. Apparently this driver does indeed support the PCMCIA card in my system. Once I get it to compile that is. The ideal alternate would be a pre-compiled version, but I sense there are no such things out there just now. Just a guess, though. I admit total ignorance on the whole shebang. Someone once said "Ignorance is bliss". I think I finally understand.
We're always looking for ways to put back into the community some of the joy and friendship we take out. In Vancouver we discovered my seester has an Asian student whom she boards. The parents send money to cover the costs of room and board, and the student gets to experience a different culture and learn the language. Cool idea we thought. And a way we can pay back into our community. So this afternoon Leah phones the local high school and asks if they have such a program. Yes, they do -- here's the coordinator's name... Leah phones him, explains that we'd like to be involved in the program. We both fully expect the process to take several months to put into play; if indeed they find our meager accomodations worthy. The coordinator of the program shows up at our door a few hours later (Mmm. Odd?) He talks to us for half an hour, takes a tour of the house, and is suitably impressed. He has a problem and wants to know if we can help. He has a grade 10 student arriving Sunday night, and she does not yet have a home (??). Can we help. Would we be willing to take said student on such short notice?
[count aloud: One thousand and one, one thousand and two... ]
Yes, if it will help, we will do our best to welcome the student into our home. Sunday night.
Have I mentioned lately that we enjoy life's challenges?
So. Find a way to put Danielle and Landon in our room so they don't feel out of sorts. Prepare the now empty bedroom of Danielle and Landon for the arrival of our new guest. Put some Korean snacks in the pantry so she feels welcome. Clean room, wash walls. Put contents of ex-Danielle and Landon's clothes cupboard into... ??? (Oh Dear). Finish tutorial due in... less than six hours. Finish two more tutorials due tomorrow.
And,
A partridge in a pear tree.
Good grief. When will I learn....
-oOo-
The
older I get, the more I forget. Bother.
I found this snap in my archives, and I can't for the life of me remember where I originally found it. I know I saved it because it was one of those -- GEE, I GOTTA have me one of 'em... thingies, but...
Sign. Oh well. If anyone's seen this mug in passing somewhere and can point me to where I can order one, please do (Isn't it just me? <grin> On the back porch, laptop in the lap, sipping java from my WTF mug, and planning the day ahead).
Yes, I know. I'm an imbecile. And as my friend Brian would say, Damn proud of it...
My mind blanked. I was not running on all eight cylinders. What can I say? Google is indeed a marvelous search engine. Thank you to everyone who found my "lost" mug (the correct answer is http://www.thinkgeek.com -- actually, a pretty neat site. Lots of expensive eye candy. Be warned: ThinkGeek is a time-sink).
I am still right up to my armpits in the piece I was supposed to have edited, translated to XML, compiled into the appropriate format, and submitted last night. I'm still editing. It is a slow and painful process. I gave up asking the author to clean up his scrawlings; he evidently does not possess the skills to do so. Which means *I* have to rewrite the material. I'm not amused.
Oh well. Perhaps after another 100 or so fix-the-mess projects I'll be anointed with the much-sought-after Master Editor title. Or is the Sir Editor? Editor-at-Arms?
Whatever. I'm not getting much done by prattling on here. Onward into the fray.
Just to show you I haven't completely lost my sense of humor, here's a snap to reflect on during your Friday morning drive to work -- the latest in Fall fashion from Landon. Note how the dress is finished with the requisite Pooh and Piglet adornments. I'll try to drop in later, but no promises. It's going to be another very long day.
Good morning and welcome to the weekend -- for those people who have such a thing in their life. Me? The days all seem to kinda run into each other... and the nights too.
I worked until almost 10 last night putting the final touches on two tutorials. That leaves one more -- which was officially due Thursday. While I do my best to meet submission dates, I will not release something that's not properly cooked simply to say I was punctual. I admit, however, that I'm getting really tired of seeing this document on the screen in front of me. The Tutorial from Hell. Feh. I'm going to do my utmost to get it finished this morning. I've finally got sentence construction and word usage cleaned up so the information being presented comes across rather than "WTF is he trying to say?", so now it's just a matter of transforming the Word doc to XML and making it compile. Yeah, I know... Just...
-oOo-
Yesterday Leah gave new meaning to the now infamous phrase, "Thompson Deep Clean™". She spent most of the day methodically removing the contents of every single upstairs cupboard, placing everything on the counter (or floor), throwing out (or putting in a box for the handicapped) all non-essentials, and putting what remained back as efficiently --space wise-- as possible. We have a new member joining our household Sunday night -- a grade 10 exchange student from Korea. But it's not enough to just ensure she has a room to study and sleep in. We also need to make sure there's room for the incidentals. And in our small townhouse, that means utilizing (HAH, take THAT Tim O'Reilly) every single inch of space... er... as efficiently as possible (I'm allowed to repeat words in a paragraph because it's my bar, and my boat).
What am I prattling on about?
Well, in addition to her clothes, toiletries, and personal items she'll need someplace to put:
Her winter coat and boots. This is Saskatchewan after all. And winter's just around the corner. The design of our townhouse is not the best, and our hall "coat" cupboard was already bursting at the seams. We don't have the luxury of a "mud room", so that means everyone's shoes and boots get removed in the tiny landing just inside the front door. Some reshuffling was in order.
She'll need some room in the pantry for her favorite foods (Korean or Western).
She'll need someplace to put all the textbooks she'll receive the first day of school.
She needs internet/email access (HAH, now there's one I can handle and it doesn't require any additional space!) so she can correspond with her family in Korea.
She needs a desk with good lighting to study at. We'll buy her a desk once I figure out where the hell to put it. Bother.
Speaking of toiletries, she'll need a place to put all said stuff that's out of Landon's reach. Mmm. Another one for the backburner.
As you can see, we need to provide more than just a bedroom. We need to find places to put all her "stuff". More like we need to anticipate what she might bring and/or need, and finger out where to put it and/or make it available.
-oOo-
Some interesting and insightful mail arrived from John Biel yesterday on the topic of my new wireless router/AP (Access Point).
Glad to see everything went without a hitch!!
"Two minor issues to note: One, the cable required to uplink between my existing LAN/router and the new wireless AP has to be a cross-over cable"
If you check the back of the 4 port router you'll notice that in fact there are 6 ports, 1 WAN and 5 LAN, 2 of the 5 (#4 and uplink) are in fact one port, 1 wired as a cross-over and 1 wired as a straight-thru. They can't both be in use. Linksys set it up so that you don't need a cross-over cable, you just use whichever port works with the cable you have. In your case if you're going to the uplink port on the 8port you would use port #4, if you're going to a regular port on the 8 port you would use the uplink port on the wireless. (Possibly your Out-of-the-box experience was tooo good <BG> you never needed to look at the included manual :)
John
And indeed John is absolutely correct. I unplugged my valued cross-over cable and plugged a standard CAT5 cable into the above mentioned port and Presto Pocus. Lights, camera, and action. When I first rec'd my box of goodies from Linksys, I was so pleased by the fact I added a whole wireless segment to my LAN in less than 25 minutes that when I found I needed a cross-over to make it work I simply changed cables without R'ingTFM. Thanks for heads-up, John. The Linksys BEFW11S4 wireless AP is definitely a well-designed product. I fear I'm going to have to buy it when my eval period runs out...
It has been a VERY long day.
Our new guest Susie (susie@syroidmanor.com if you care to drop her a line) is settled. And her mother is duly impressed. Oh yes. Forgot to mention. We were informed that her mother was accompanying her [her being our student]; would we be interested in putting her up as well for three days?
No not at all. Lets see now. We've just moved our children out of their room, cleaned every cupboard in the house, thrown out at least half the stuff we promised last year to keep for ever and ever amen. And... [blank]
Sure, tell her she's welcome.
Have I mentioned lately that it's been a long day?
The decks are swabbed. The sails are in order. The boat is pointed into the wind, and I finally managed to install Slackware on my notebook.
Huh? Where did Slackware come from? In the midst of touching up the hall, assembling the kids bunk beds on our room, celebrating Sunday (??), and looking for that damn partridge (which, once again, has alluded me -- Bother).
Yep. Slackware boots. I have no idea why I scrubbed a perfectly good working version of SuSE off my HD; perhaps it was all that talk from Bilbrey. Talk of trying new distros and rising to fight another day.
Sigh. I made it happen, although the process was totally unintuitive. Hint: DO NOT follow the defaults; they will get you in a world of hurt.
I'll be back next week. Which is tomorrow. Which is actually today -- just a tad later in the day...
Cheers.
Send questions or comments about this
site to
webmaster@syroidmanor.com.
Copyright © 1998, 1999, 2000, 2001 Tom Syroid. All Rights Reserved
Last modified:
August 27,
2001